Hi,

I've noticed an issue with our 64bit machines, running 32bit installs of Office 2013 and using OneDrive for Business integration.

In short, upon loading Word, the connected services look as they should but if I try to browse OneDrive For Business it opens up an Explorer window to the users mapped H:\ drive (which points to network storage) rather than navigating to the OneDrive for Business storage location.  It also does this if I click on the recent folders for the OneDrive account.

This does not seem to happen on the 32bit machines.

Any help would be appreciated, we're thinking something is off with the user profiles perhaps - we are using roaming profiles.

Thanks

Hi,

Does the user have OneDrive for Business installed and configured in local?

Please provide some snapshots about the issue, so that I can understand the scenario better. Please send the images to our email address:

ibsofc@microsoft.com

Please add the url of this thread in the email for easy tracking.

Regards,

Melon Chen
TechNet Community Su

Hi Melon,

The local installs of Office 2013 are the full package, minus the SkyDrive Pro component, if that's what you mean?  Obviously the installations were done before the name change to OneDrive for Business, could this be causing an issue?  We don't want the SkyDrive/OneDrive client installed locally.

I have run through the process with PSR recording, so will email you the file now.

Thanks

Andy

Hi,

Just wondering if you'd had a chance to look through the Problem Steps Recorder I sent you, or even if the email had got through?

We are looking to roll out Office 365 with OneDrive shortly and need it working on our entire estate.

Regards

Andy

I have narrowed down this issue to being related to our Folder Redirection for Desktops.

We have a GPO in place that redirects user Desktops to a server location.  When this policy is active, the OneDrive browse within Office 2013 points to the user Home directory.  This only happens on our 64bit machines.  We are doing the Folder Redirection using the built-in Windows Setting in User Configuration Policies.

Can anyone suggest a reason for this?!